Repository navigation
🧹 chore: run dagger call with --cloud - #16
Merged
Merged
Conversation
Route every Dagger CLI invocation in GitHub workflows through Dagger Cloud provisioned engines/machines by appending the global --cloud flag. The DAGGER_CLOUD_TOKEN secret is already supplied to each step.
jpmcb
marked this pull request as ready for review
September 24, 2026 21:46
 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
👨🏼
Local DeepSeek fanout.
Refs PCC-1489
🤖
Appends the global
--cloudflag to everydagger callinvocation in.github/workflows/, so CI runs on Dagger Cloud provisioned engines/machines.DAGGER_CLOUD_TOKEN, so no environment changes are needed.dagger call test --silent --cloudconvention.